-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
r/aws_redshift_cluster: Trigger ForceNew aws_redshift_cluster on encrypted change #1120
r/aws_redshift_cluster: Trigger ForceNew aws_redshift_cluster on encrypted change #1120
Conversation
Hi @minamijoyo I am going to pull this locally and add a test that shows this works as expected. Hope this is ok with you? Thanks Paul |
ok, I take that back - this is going to be difficult to add an automated test for :) |
@stack72 Thank you for reviewing and merging. And I'm very sorry for troubling you. An automated test is not easy because it takes a long time to regenerate the cluster, but as long as I tried it manually it works as I expected. I will attach manual test logs for confirmation. provider "aws" {}
resource "aws_redshift_cluster" "default" {
cluster_identifier = "tf-redshift-cluster"
master_username = "foo"
master_password = "Mustbe8characters"
node_type = "dc1.large"
cluster_type = "single-node"
skip_final_snapshot = true
encrypted = false # Change this false to true
}
Thanks. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Fixes #1119